Bank Account - COP
Introduction
This section covers the COP (Colombian Peso) utility endpoint used to look up information about a Bre-B key before referencing it in a ticket or registering it on a beneficiary.
For sending COP via Bre-B you can either:
- Register a beneficiary with a
breBKey(see Beneficiaries Bank Accounts > Bank Guide COP) and reference it by id in the ticket, or - Pass the
breBKeyinline in the ticket payload — the key is validated automatically at ticket creation time.
The endpoint below lets you validate a key on demand (e.g., to show the holder name to your end-user before they confirm the operation).
To receive COP, each account can also have a fixed Bre-B key that receives any amount, with no ticket created first, and is credited as USDC. Read it from the bre-b field of Account Info. Available in sandbox. See Static Deposits.
Bre-B cap: Bre-B transactions are limited to 3,000 USDC on either leg — payin or payout. Larger amounts are rejected with Bre-B transactions are limited to 3000 USDC (HTTP 400). A valid key is no guarantee the amount will clear; route larger transfers through PSE (BANK-TRANSFER).
A COP quote is an international transfer, against BRL or crypto: add the BCB purpose code of that leg to it, outputPurposeCode when you pay out in it and inputPurposeCode when you receive it. It is optional through November 14, 2026 and required from November 15, 2026. See International Transfers (ACAM).
Get Bre-B Info
The Bre-B Info endpoint validates a Bre-B key against the Bre-B network and returns the linked holder information when the key is registered. Mirrors the PIX Info pattern.
Parameters
| Field | Type | Description |
|---|---|---|
| breBKey | string | The Bre-B key you would like to look up. |
Endpoint
Request example:
curl -X GET "https://api.sandbox.avenia.io:10952/v2/account/bank-accounts/cop/bre-b-info?breBKey=@CBW0ZWQT6" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer eyJhdXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
Response
{
"holderName": "San*** Te****",
"holderIdNumber": "*****1234"
}
Response Fields
| Field | Type | Description |
|---|---|---|
holderName | string | Masked holder name. |
holderIdNumber | string | Masked holder document number. |
Errors
| Status | When |
|---|---|
404 | The key is not registered on the Bre-B network. |
400 | breBKey query parameter is missing or malformed. |
Conclusion
You now have the necessary understanding to validate a Bre-B key before consuming it in a ticket or beneficiary registration within the Avenia API.